In this technologically advanced world, we are plagued by one thing: Microsoft Windows. Don't you just hate Windows users? Don't you just wish there was something you could do to make them wish they had chosen the better operating system? (The Mac OS!) Well, now there is a way. Read on.
This Article should include the following files:
Nuke'Em (Including the Program, Readme and HTML files)
winnuke.c
winnuke.pl
Winnuke Explained
A guy who calls himself "_eci" wrote a program called "Winnuke". What this program does is it connects to a target machine on a network, and sends Out Of Band Data (OOB). This data can be anything (in the original program it was the text "bye"). This attack is called "Denial of Service (DoS)".
Windows supports OOB, but it doesn't know what to do with the data. For example, Windows 95 tries an exception handler, which fails, leaving the Windoze user with a blue screen. The 3 different OSes it targets (95, NT, 3.11) do different things. Anything from losing network connections to blank screens can happen, depending on how the system is set up.
This attack can target any port that listens for data, but the popular one is the NetBIOS port (139). The NetBIOS is built into every PC. It performs the basic networking functions. The identd port (113) is also possible.
The Nuke Files
• Nuke 'Em (Mac)
• Winnuke.c (C/UNIX)
• Winnuke.pl (Perl/UNIX)
Nuke 'Em
In my opinion, Nuke 'Em is the best Mac Winnuke there is right now. (I am currently working on a spiffy version myself, but that's still in the works amongst countless other projects) Anyway, here is how to use Nuk 'Em.
It's actually pretty easy. Once you start it, press Command-N or choose "Nuke 'Em..." from the File menu.
Once you've done that, you get this dialog box:
 
Where it says "Host:", put the IP address. The IP address will either be a long number seperated by periods, like "209.170.50.76", a domain name like "microsoft.com" or a combo like "9062-irc.van.direct-96.ca". Nuke'Em should support all three, but some versions of Winnuke only support completely numerical ip addresses! (That's important)
A cool thing you can do with Nuke'Em is you can use it as a CGI. That is, if you have a web server running off your Mac you can link it to your page. This will only work if it's running on a Mac. The instructions for this are in the Nuke 'Em docs.
Winnuke.c (UNIX)
If you are cool, you'll have a shell account somewhere. (If you are really cool you'll have UNIX running on your own computer.) Anyway, this is a better alternative to using your Mac because if you nuke somebody through telnet, it doesn't tie up your computer. (You can even write a shell script to do it again and again and again, but I won't show you that...)
Okay, using Fetch (My FTP prog of choice), upload "winnuke.c" to your directory. Now, telnet to your shell. Once you are in, type:
% cc -o nuke winnuke.c
% = The C-shell prompt.
cc = The command to compile.
-o = Means "Name the program <name that follows"
nuke = What we named our program.
winnuke.c = What we compiled.
NOTE: This program is only guaranteed to work on BSD, Linux and SunOS.
Now, to execute it, type:
% ./nuke microsoft.com
NOTE: "./nuke" is 1 word. This is how you execute a custom program in UNIX. ANOTHER NOTE: I'm actually not sure about the dot-slash thing. I only have experience with BSD, so I'm not sure if the Linux/SunOS command is different.
Winnuke.pl (Also UNIX, but Perl this time)
An alternative to C is Perl, which programming genius "_eci" also did. You can use the C version or the Perl version, it doesn't matter, but any Perl gurus might be interested to see how it was done and stuff. Sooooooo, here's how to use it:
First find out the path to Perl on your UNIX server. Then replace the:
#!/bin/perl
with whatever the path is.
NOTE: Don't forget the "#!" before the path name.
Upload "winnuke.pl" using Fetch. (I stress this...all the other FTP programs suck...)
So what we've done is renamed our .pl file to something easier and quicker to type, and then changed it to an executable.
NOTE: Once again, I'm not sure about the rules concerning the execution of programs using "dot-slash" in types of UNIX other than BSD. You'll have to ask someone familiar to your brand.
Winnuke How - 2
Ok, here are some cool ways to use Winnuke:
At my school our computers are running on a Win95/NT combo. Since we have to share our hard drives for networking exercices, it's setup is each computer in the school has it's individual local IP address. They are in the format
"connection##.<group>"
Each computer has a name like "cs12" or whatever. So, to target computer "cs12" in the computer lab, I would type:
"connection12.students"
as the IP address. (Other ones to try are "teachers", "office", and "library") But students is the most fun and least dangerous.
Another neat trick to do is to nuke "127.0.0.1", which is the IP address for your own machine. (Sometimes on some local-area networks this will work) Find out the individual IP addresses at your office/school and try it out.
When using IRC, you may get the occasional asshole who comes into #mac-talk and starts pissing everyone off by saying stuff like "macs suck! macs are shit!". Instead of immediatly flaming him back, type:
/whois macflamer
And you'll get a bunch of useful info. What you need now is the numbers after the "@" and his nick. For example, we are looking for the string:
macflamer@connection321.6969.boring.isp.net
We copy it, and paste it into Nuke'Em or Winnuke or whatever. Wait a minute or two, then try again.
Closing
Well, this is the first article I've actually finished for Hackaddict. Winnuke will not actually harm the computer you use it on, but it will sure screw it up for a while. A restart usually fixes the problem though.
So anyway, have fun nuking your PC enemies, friends, bosses, teachers, etc.
- Fuzebox
fuzebox@cyberdude.com
** Now for the Late breaking news!!! **
A close friend of mine, who goes by the handle of "Zulu" was busted at our school for completely screwing up our NT network server. However, he was unfairly judged and punished. The network admin had just spent an entire week reinstalling Windoze NT on the network server. He had just cleared Duke Nukem out of everyone's directories, when he came across Winnuke for Windows 95. Naturally, with angry teachers and principals breathing down his neck for a reason for the server being down, he grabbed this as a golden oppurtunity. After all, if the shoe fits...
To make a long story short, my poor Windoze-using friend has his account suspended for 4 months. He is not allowed back in the computer labs for an entire month. He will not get any Internet access for the rest of the year. Finally, he has to do "community service", meaning go through and patch every copy of Windoze against winnuke, and then clean up their hard drives and install foolproof on each one. EACH COMPUTER IN THE SCHOOL!!!
There are two lessons to be learned here:
Lesson #1:
Don't use Wndoze. Persuade your school not to use Windoze. It is nothing but trouble.
Lesson #2:
Don't get careless, don't get caught. My friend tried using conventional Windoze 95 techniques to hide his files. Problem was our admin is a Windoze guru. Our school has no UNIX guru (Or at least one who cares anyway) so I stayed safely out of trouble. DON'T GET CAUGHT.
Conclusion Number Two
So the genius sysadmins decided that the harmless Winnuke damaged their network server...From this little incident they have no doubt had their salaries raised a couple grand. And now my friend has to suffer. So even though Winnuke is harmless, those who are less intelligent will find it as a threat. So be careful.
